Skip to main content

C# : Securely Encrypting and Decrypting AppSettings Values in ASP.NET Core


Ensuring the security of sensitive data, such as connection strings or API keys, stored in configuration files like appsettings.json is crucial for any application. In this blog post, we'll explore how to encrypt and decrypt values in appsettings.json using ASP.NET Core, providing end-to-end code examples and explanations.

Step 1: Create a .NET Core Web Application: Begin by creating a new ASP.NET Core web application in Visual Studio or through the command line:

dotnet new web -n MyApp
cd MyApp
Step 2: Install Required Packages: To encrypt and decrypt values, we'll use the System.Security.Cryptography namespace. Ensure the following package is installed:
dotnet add package System.Security.Cryptography.ProtectedData
Step 3: Implement Encryption and Decryption Logic: Create a helper class to handle encryption and decryption operations:
using System;
using System.IO;
using System.Security.Cryptography;
using System.Text;

public class EncryptionHelper
{
    private const string entropy = "YourEntropyValue";

    public static string Encrypt(string plainText)
    {
        byte[] plainBytes = Encoding.UTF8.GetBytes(plainText);
        byte[] encryptedBytes = ProtectedData.Protect(plainBytes, Encoding.UTF8.GetBytes(entropy), DataProtectionScope.CurrentUser);
        return Convert.ToBase64String(encryptedBytes);
    }

    public static string Decrypt(string encryptedText)
    {
        byte[] encryptedBytes = Convert.FromBase64String(encryptedText);
        byte[] plainBytes = ProtectedData.Unprotect(encryptedBytes, Encoding.UTF8.GetBytes(entropy), DataProtectionScope.CurrentUser);
        return Encoding.UTF8.GetString(plainBytes);
    }
}
Step 4: Encrypt AppSettings.json Values: In your appsettings.json, encrypt sensitive values using the Encrypt method:

{
  "AppSettings": {
    "ConnectionString": "#{EncryptedConnectionString#}"
  }
}
Step 5: Decrypt AppSettings.json Values at Runtime: Decrypt the encrypted values during application startup and replace placeholders:
using Microsoft.Extensions.Configuration;

public class Startup
{
    public IConfiguration Configuration { get; }

    public Startup(IConfiguration configuration)
    {
        Configuration = configuration;
        DecryptAppSettings();
    }

    private void DecryptAppSettings()
    {
        var encryptedConnectionString = Configuration["AppSettings:ConnectionString"];
        if (encryptedConnectionString.StartsWith("#{EncryptedConnectionString#}"))
        {
            Configuration["AppSettings:ConnectionString"] = EncryptionHelper.Decrypt(encryptedConnectionString.Substring(23));
        }
    }
}
Step 6: Use Decrypted Values in Your Application: Now, you can safely use the decrypted values in your application:
using Microsoft.Extensions.Configuration;
using Microsoft.Extensions.DependencyInjection;

public class Startup
{
    public IConfiguration Configuration { get; }

    public Startup(IConfiguration configuration)
    {
        Configuration = configuration;
        DecryptAppSettings();
    }

    private void DecryptAppSettings()
    {
        var encryptedConnectionString = Configuration["AppSettings:ConnectionString"];
        if (encryptedConnectionString.StartsWith("#{EncryptedConnectionString#}"))
        {
            Configuration["AppSettings:ConnectionString"] = EncryptionHelper.Decrypt(encryptedConnectionString.Substring(23));
        }
    }

    public void ConfigureServices(IServiceCollection services)
    {
        // Use decrypted values
        var connectionString = Configuration["AppSettings:ConnectionString"];
        services.AddDbContext<MyDbContext>(options => options.UseSqlServer(connectionString));
    }
}
Conclusion: Encrypting and decrypting sensitive values in appsettings.json ensures the security of your application's configuration data. By following the steps outlined in this guide, you can seamlessly integrate encryption and decryption logic into your ASP.NET Core application, safeguarding sensitive information from unauthorized access.

Comments

Popular posts from this blog

Implementing and Integrating RabbitMQ in .NET Core Application: Shopping Cart and Order API

RabbitMQ is a robust message broker that enables communication between services in a decoupled, reliable manner. In this guide, we’ll implement RabbitMQ in a .NET Core application to connect two microservices: Shopping Cart API (Producer) and Order API (Consumer). 1. Prerequisites Install RabbitMQ locally or on a server. Default Management UI: http://localhost:15672 Default Credentials: guest/guest Install the RabbitMQ.Client package for .NET: dotnet add package RabbitMQ.Client 2. Architecture Overview Shopping Cart API (Producer): Sends a message when a user places an order. RabbitMQ : Acts as the broker to hold the message. Order API (Consumer): Receives the message and processes the order. 3. RabbitMQ Producer: Shopping Cart API Step 1: Install RabbitMQ.Client Ensure the RabbitMQ client library is installed: dotnet add package RabbitMQ.Client Step 2: Create the Producer Service Add a RabbitMQProducer class to send messages. RabbitMQProducer.cs : using RabbitMQ.Client; usin...

How Does My .NET Core Application Build Once and Run Everywhere?

One of the most powerful features of .NET Core is its cross-platform nature. Unlike the traditional .NET Framework, which was limited to Windows, .NET Core allows you to build your application once and run it on Windows , Linux , or macOS . This makes it an excellent choice for modern, scalable, and portable applications. In this blog, we’ll explore how .NET Core achieves this, the underlying architecture, and how you can leverage it to make your applications truly cross-platform. Key Features of .NET Core for Cross-Platform Development Platform Independence : .NET Core Runtime is available for multiple platforms (Windows, Linux, macOS). Applications can run seamlessly without platform-specific adjustments. Build Once, Run Anywhere : Compile your code once and deploy it on any OS with minimal effort. Self-Contained Deployment : .NET Core apps can include the runtime in the deployment package, making them independent of the host system's installed runtime. Standardized Libraries ...

Clean Architecture: What It Is and How It Differs from Microservices

In the tech world, buzzwords like   Clean Architecture   and   Microservices   often dominate discussions about building scalable, maintainable applications. But what exactly is Clean Architecture? How does it compare to Microservices? And most importantly, is it more efficient? Let’s break it all down, from understanding the core principles of Clean Architecture to comparing it with Microservices. By the end of this blog, you’ll know when to use each and why Clean Architecture might just be the silent hero your projects need. What is Clean Architecture? Clean Architecture  is a design paradigm introduced by Robert C. Martin (Uncle Bob) in his book  Clean Architecture: A Craftsman’s Guide to Software Structure and Design . It’s an evolution of layered architecture, focusing on organizing code in a way that makes it  flexible ,  testable , and  easy to maintain . Core Principles of Clean Architecture Dependency Inversion : High-level modules s...